-
Notifications
You must be signed in to change notification settings - Fork 823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eks-prow-build-cluster: create simple monitoring stack #5011
eks-prow-build-cluster: create simple monitoring stack #5011
Conversation
|
Welcome @pkprzekwas! |
Hi @pkprzekwas. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
On top of that I've tested the AWS native Container Insights. Installation is trivial but it requires modifying terraform script in order to extend permissions of instance profiles. At the moment any modifications to EKS terraform script are blocked by #4989. Once it's merged, Container Insights can be enabled in a separate PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks pretty good to me. I left some questions and comments, most of them should be just nits.
kubectl --namespace monitoring port-forward svc/prometheus-operated 9090 | ||
|
||
# Grafana | ||
kubectl --namespace monitoring port-forward svc/grafana 3000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we expose this Grafana instance publicly? If yes, let's create a follow up issue to track that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure if this is something that we want to maintain in a longer term. IMO we can expose it for now till we haven't figured which monitoring solution works the best for both GCP and AWS clusters.
I wonder if there were other things we want to expose over time, in which case ingress-controller would be handy.
infra/aws/terraform/prow-build-cluster/resources/monitoring/cadvisor/cluster-role.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/cadvisor/ds.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/grafana/datasources.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/node-exporter/cluster-role.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/node-exporter/ds.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/node-exporter/service-monitor.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/prometheus-main/sa.yaml
Outdated
Show resolved
Hide resolved
infra/aws/terraform/prow-build-cluster/resources/monitoring/grafana/config.yaml
Show resolved
Hide resolved
…nts, enable honoring labels
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me!
/lgtm
/approve
/assign @ameukam
for approval
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, pkprzekwas, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR brings simple monitoring setup for Prow EKS cluster. At some point we will replace it with sth more sophisticated (like kube-prometheus). For now, in order to debug migration of prow jobs, this is hopefully enough.
PR contains:
monitoring
namespace/assign @ameukam @upodroid @xmudrii
This stack has been already deployed to
prow-build-cluster
. Part of #4686